Release 10.1A: OpenEdge Development:
Web Services

Arrays

OpenEdge maps arrays of simple types to Progress 4GL arrays. The WSDL Analyzer determines that it must map to a Progress 4GL array when it recognizes a SOAP array declaration or the use of the minOccurs and maxOccurs XML Schema attributes in a parameter type definition. If a SOAP array is declared as unbounded, the Analyzer maps it to a Progress 4GL array with an indeterminate extent.

When it receives a SOAP response that includes a sparse array parameter, OpenEdge creates a Progress 4GL array of the appropriate size and fills it. OpenEdge sets each unused entry in the Progress 4GL array to the Unknown value (?).

OpenEdge never passes a sparse array as input to a Web service.

For arrays of complex types, the Progress 4GL represents them as one of the following data types, depending on the structure and content of the complex data, as determined by the WSDL Analyzer:

A temp-table parameter.
A ProDataSet parameter.
A LONGCHAR (LONGCHAR[ ]) or CHARACTER (CHARACTER[ ]) array parameter.

Depending on how the Analyzer represents it, you might handle the entire array or individual elements as a complex data type (see the "Complex data types" section). For more information on how the WSDL Analyzer determines the representation of complex data, see the "Analyzing complex data" section.